Processing a mobile payload

ABSTRACT

In one aspect, a method includes receiving, from a sender device, a request to initiate a transfer of an asset to a recipient; causing a user interface to be presented on the sender device to receive an input of an amount of the asset to be transferred; causing an indication of the transfer of the asset to be presented via the user interface in association with a graphical icon representing a gift wrapping that conceals at least some information regarding a payload associated with the transfer; associating the graphical icon with the payload to generate a gift-wrapped element that includes the amount and the information regarding the payload; causing a notification to be sent to a recipient device of the recipient that includes the gift wrapped element; and causing assets in the amount to be withdrawn from an account of the sender and transferred to an account of the recipient.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation Application of U.S. patentapplication Ser. No. 17,174,277, filed on Feb. 11, 2021, which is aContinuation Application of U.S. patent application Ser. No. 15/851,423,filed on Dec. 21, 2017, now U.S. Pat. No. 10,949,829, which is aContinuation Application of U.S. patent application Ser. No. 15/282,833,filed on Sep. 30, 2016, now U.S. Pat. No. 9,881,296 which claimspriority to U.S. Provisional Patent Application No. 62/393,504, filed onSep. 12, 2016, all of which are hereby incorporated by reference intheir entirety.

BACKGROUND

Users can send money through variety of online services, such as onlinechecking accounts or online payment methods. Using these online paymentmethods may be a complex and time-consuming process that often involvesinputting various financial information (e.g., bank account numbers or arouting number), identification verifications (e.g., social security ora home address), and information to identify the recipient at the timeof the payment (e.g., an address or account number). In many instances,the payor's knowledge regarding a recipient may be limited to a mobilenumber, therefore providing financial information or otheridentification verifications may be impossible. Additionally, while apayor is communicating with a recipient using a messaging or socialnetworking application on a computing device (e.g., mobile phone), thepayor may be required to execute a new application on the computingdevice in order to send a payment to a recipient. Using conventionalsystems, it can be challenging to transfer funds between individualsthrough non-conventional data transfer platforms.

DESCRIPTION OF THE DRAWINGS

Non-limiting embodiments of the present disclosure are described by wayof example with reference to the accompanying figures which areschematic and are not intended to be drawn to scale. Unless indicated asrepresenting the background art, the figures represent aspects of thepresent disclosure.

FIG. 1 illustrates an example of a system for processing mobilepayments, according to an embodiment.

FIG. 2 illustrates a flowchart depicting operational steps of a methodfor processing a mobile payment request, according to an embodiment.

FIG. 3 illustrates a flowchart depicting operational steps of a methodfor generating a mobile payment request, according to an embodiment.

FIG. 4 illustrates a flowchart depicting operational steps of a methodfor a receiving and transmitting a mobile payload, according to anembodiment.

FIG. 5A-F illustrate a graphical user interface (GUI) for generating,transmitting and receiving a mobile payment request, according to anembodiment.

DESCRIPTION

Modern telecommunications systems offer several ways for mobile devicesto communicate with one another instantly, using a variety of protocols,such as simple message service (SMS) and multimedia message service(MMS), as well as other instant communications platforms hostingreal-time inter-device communications. But SMS and other simple or plaintext communications protocols utilized by cellular telephones are oftenlimited in their capabilities beyond sharing simple text messages,graphics, or short videos. As such, conventional messaging betweenmobile devices is not a useful mechanism for transferring funds betweenindividuals, even though the instant communications would make thismedium for communications between devices a potential candidate forreal-time or real-time transfer of funds or other data.

Additionally, recent technological advances have resulted in an increasein digital currency and have inevitably created new technologicalchallenges regarding transactions involving such currencies. As aresult, a new type of problem exists: how to send digital money toanother with ease and security. Current payment methods and processesfor mobile devices provide little flexibility and ease for sendingpayments between mobile devices, such as online funds transfers, ACHpayments, and the like. As a result there is a need for a technicalsolution for this problem. The embodiments described herein aim toprovide a method and a system for a secure and easy payments using amobile device and existing telecommunications and network (IP-based)infrastructures.

Until recently, however, existing mobile telecommunications technologieshave been limited by the outmoded protocols (e.g., SMS, MMS) and thedevice applications that interact with these protocols (e.g., textmessage applications). The devices were therefore only capable oftransmitting simple messages or graphics (e.g., GIF images) from onedevice to the other. There would have been no means of conducting asophisticated fund transfer. New communications technologies are beingintroduced, whereby the communications protocols permit moresophisticated data transfers and the device applications may facilitatemore complex interactions between the devices through, what users wouldperceive as, a conventional instantaneous text messaging medium. Theembodiments disclosed herein provide systems and methods that, throughinterconnected mobile devices, marry the financial institution networkedsystems that host and facilitate funds transfers between large scalefinancial systems, together with an instantaneous messaging host systemthat facilitates data transfers between the mobile devices through oneor more protocols.

As an example, in some embodiments, a payment processing server isconfigured to receive a payment request from a mobile device. Thepayment processing server receives a request to send a payment (e.g., apayment request) from a payor's mobile device's instant messagingapplication. The payment request may contain information, such as anamount to be paid and identification of the payor. Often the messagingsystem keeps the recipient's device information or identifier (e.g.,phone number, MAC address, IP address) secret from the payor's deviceand/or the payment processing server; as such, the payment processingserver may not receive nor transmit any identification data associatedwith the recipient. The payment processing server may communicate with afinancial account held at a financial institution, through which thepayment processing server may decrement a payor's financial account,create an escrow account, and/or increment the balance value based onthe payment request. The payment processing server may also generate atoken string data regarding the escrow account such as an alphanumericstring based on a random value generator. In some instances, the paymentprocessing server may further generate and return to the payor's mobiledevice various types of information transmitted via the messagingservice, such as a payload with a hyperlink containing the token string,an image associated with the amount of the payment request, and a textinstructions. The payment processing server may transmit the payload tothe payor's mobile device's instant messaging application. The paymentprocessing server may further pay the recipient, by incrementingrecipient's financial account, as a result of the recipient receivingthe payload and activating the hyperlink of the payload.

In some embodiments, a messaging server facilitates mobiledevice-to-mobile device funds transfers or payments through a messagingservice hosted by the messaging server through a third-party applicationhosted by the mobile device and associated with the payment processingserver. In operation, a mobile device may generate a user interface (UI)that comprises a first screen portion that displays and transmits textmessages or other types of data via a hosted instant messagingapplication. The UI may also comprise a second screen portion to accessa third-party application executed locally on the mobile device and isassociated with the payment processing server. The second portion of theUI allows the user to input various options that are then sent to thepayment processing server as instructions to populate a payload andreceive an inputted amount in the second screen portion (for thepayload). The mobile device may transmit the payment request andidentification of the payor to the payment service system and receive apayload comprising a hyperlink containing a token string, an image basedon the amount of payment request, and text instructions for the paymentrequest. The mobile device may further populate a message to therecipient comprising the payload where the payload does not includeinformation regarding the recipient. The mobile device may also transmitthe payload to the recipient via an instant message.

A recipient's mobile device may receive a message containing a payloadfrom a mobile device network, as prompted by a payor's mobile device.The payload may comprise a hyperlink that contains a token string, animage based on a payment request amount, and text instructions to therecipient. When the recipient activates the payload, the recipientmobile device transmits instructions to a payment processing server torelease funds to a designated financial institution account system.Activation of the payload occurs, in some embodiments, when therecipient activates a hyperlink that contains a token contained withinthe payload, by clicking on the hyperlink. The payment processing serverconfirms the activation of the payload and the amount of the payment ina database of the payment processing server, and then the paymentprocessing server facilitates the transaction by releasing the funds tothe designated financial institution account system.

The present disclosure is described in detail with references toembodiments illustrated in the drawings. Other embodiments may be used,or other changes may be made without departing from the spirit or scopeof the present disclosure. The illustrative embodiments described in thedetailed description are not meant to be limiting of the subject matterpresented here. Various embodiments will now be described in furtherdetail. The following description provides specific details for athorough understanding and enabling description of these embodiments.One skilled in the relevant art will understand, however, that theembodiments discussed herein may be practiced without many of thesedetails. Likewise, one skilled in the relevant art will also understandthat the embodiments may include many other obvious features notdescribed in detail herein. Additionally, some well-known structures orfunctions may not be shown or described in detail below, to avoidunnecessarily obscuring the relevant description.

FIG. 1 illustrates an embodiment of a system 100 that includes severalservers that handle various steps in the system 100 for processing apayment request from a mobile device. Note that FIG. 1 illustrates atwo-party scheme in which a payor requests payment to be sent to arecipient. Other embodiments of this disclosure may similarly functionwith different schemes involving more than two parties.

A server 104 may be positioned between a mobile device 101, a mobiledevice 102, and a system of record server 105. Server 104 is part of aPayment Processing System (PPS) 103, which may also include anApplication Programming Interface (API) 106 and one or more databases107 a-107 n. Server 104 may use API 106 to communicate with mobiledevices belonging to the payor or the recipient over network 110 (thePPS network). Databases 107 a-107 n may include information such a userprofile, account numbers, and balances. In the exemplary system 100 seein FIG. 1 , the server 104 may receive transmissions regarding paymentrequests that occur between a payor using mobile device 101, a recipientusing mobile device 102, and system of record server 105. In anembodiment, upon receiving a payment request from the payor andgenerating a payload, server 104 may forward the transaction to systemof record server 105 that is associated with a financial institute. Inanother embodiment, server 104 may directly contact the financialinstitute in order to facilitate the payment request and transaction.

System of record server 105 may be hosted by a financial institute or athird party that provides a service to the financial institute. Thesystem of record server 105 may maintain information regarding thebalance of an account maintained by the payor or the recipient at thefinancial institute. Certain parties, such as the account owner, themerchant, the issuer processor, or the PPS 103, may assume certain risksthat an account holder does not have sufficient funds to fund atransaction, until the system of record server 105 authorizes thetransaction. Upon receiving a payment request, server 104 may forwardassociated information to system of record server 105, which maintainsan account corresponding to the balance of the payor. In an embodiment,the financial institute may also generate an authorization response toforward to the system of record server 105, back through other devicesin the payment stream and eventually to the server 104 to confirm thatthe payor or recipient may complete the payment transaction. Server 104may either receive authorization from the financial institute or createa custom authorization or anti-fraud procedure in order to authorize thepayment requests.

Server 104 may also be in communication, over networks 110, with mobiledevice of the payor and the recipient. Network 110 or 111 may representa worldwide collection of networks and gateways, such as the Internet,that use various protocols to communicate with one another, such asLightweight Directory Access Protocol (LDAP), Transport ControlProtocol/Internet Protocol (TCP/IP), Hypertext Transport Protocol(HTTP), Wireless Application Protocol (WAP), etc. Network 110 may alsoinclude a number of different types of networks, such as, for example,an intranet, a local area network (LAN), or a wide area network (WAN).Payor's and recipient's mobile devices (mobile devices 101 and 102) areillustrated in FIG. 1 as smartphones, but may be any computing device,such as any mobile phone, tablet, smart watch, personal data assistant,gaming console, or personal computer.

In an embodiment, mobile device for the payor and the mobile device forthe recipient may be in direct communication in order to transmit apayment request, payload, token, or other financial informationassociated with the payment request through variety of methods and inparticular, text or instant messaging. For example, a mobile deviceserver 109 hosts a messaging service. The mobile device server 109 maygenerate instructions to mobile device 101 to populate a user interfaceand generate a payment request. The mobile device server 109 may also,utilizing network 111 (the mobile device network), communicate thatpayment request and other relevant information to mobile device 102 viatext message and instant messaging application. As described below, themobile device server 109 and PPS 103 may collaborate in order togenerate a payment request.

Referring now to FIG. 2 a flowchart depicting operational steps of amethod for processing a mobile payment request is illustrated inaccordance with an embodiment. Steps of method 200 may be implementedusing one or more modules of the PPS such as the PPS server. FIG. 2 doesnot imply any limitations with regard to the environments or embodimentsthat may be implemented. Modifications to the depicted environment orembodiment shown in FIG. 2 may be made.

At step 201, the PPS server may receive a payment request from a payor'smobile device. In this example, the PPS server may receive the paymentrequest from the payor's mobile device's instant message application forinitiating a payment. In an embodiment, the payment request may comprisean amount of money to be paid and identification of the payor. Thepayment request may, in an embodiment, not include any identification ofwho will receive the payment (i.e., the recipient). The payment requestmay be received by the PPS server through an instant messagingapplication installed on the payor's mobile device. In that embodiment,payor's mobile device's instant messaging application is linked,directly or indirectly, to the PPS server and notify the PPS server ofany payment requests originated from the payor's mobile device. In otherembodiments, the PPS server may receive a payment request through anelectronic input source when a payor interacts with the electronic inputsource to request a payment to be made. Non-limiting examples of aninput source may be spoken words (e.g., various speech recognitionsoftware), various third-party applications native to payor's mobiledevice (e.g., third-party instant messaging application or a third-partyapplication from payor's cell phone or other portable devices thatsupport the same or similar operating systems), or inputting a corpuselectronically from a computer implemented source such as anotherelectronic device. Operational steps to generate a payment request on apayor's mobile device are described in FIG. 3 .

In other embodiments, the payor may directly enter payment requestinformation into a mobile application native to payor's mobile deviceand in direct communication with the PPS server or designated tocommunicate with the PPS server. For example, PPS may have a designatedmobile application (e.g., the PPS API) for a payor and payment requestsmay be generated through said application. The PPS server may, in yetanother embodiment, automatically identify recurring payments usinginformation from a financial account associated with a payor. Forexample, if the a payor pays the same amount of money on substantiallythe same day each month or after a recurring event, then the PPS servermay identify that as a recurring payment request. For example, therecurring payment might be $100 for gas and appear around the 10th ofevery month. After a predetermined number of times for that paymentappearing, the PPS server may record the recurring payment in one ofdatabases and expect a similar payment request to be generated everymonth. In that embodiment, the PPS server may predict a payment requestand notify the payor to generate a payment request or pre-fillinformation regarding the payment request. A payor may also identifypayment requests as recurring. In another embodiment, the PPS server,may record a user's activity and previous payment requests in order tosimplify payor's generating of the payment request. For example, a payormay scroll through past payment requests in order to see previoustransactions. The PPS server may gather data from variety of sources,including but not limited to social networks and other online datasources pertaining personal information of a payor, to predict contentof a payment request.

At step 202, the PPS server may generate instructions to increment abalance value of an escrow account. The PPS server may increment thebalance value of an escrow account data record in accordance with thepayment request. In one example, the escrow account balance value may beincremented using funds in a debit card account, credit card account,savings account, checking account, credit line, or other account (e.g.,decrementing payor's account). The escrow account may be an electronicaccount held by a party associated with the PPS or a third-party onbehalf of both transacting parties or the payor. In one embodiment,neither the payor nor the recipient may modify or withdraw money fromthe escrow account without permission of the PPS. In an embodiment, oncethe value of an escrow account is incremented, the payor may notdecrement the value anymore. In another embodiment, once the value isincremented, payor's access to the escrow account is terminated. Inanother embodiment, payor may be able to cancel the payment requestprior to sending the message and the value of the escrow account may berefunded to the payor. An escrow account may be created for each paymentrequest individually, or in groups. For example payment requests may begrouped based on variety of categories and consequently based on theirrespective groups all payment requests may use the same escrow account.For instance, in the case of a payor with multiple payment requestwithin a same day, one escrow account with a value of the combinedpayment requests may be created.

The PPS server, in an embodiment, may only increment the value of theescrow account upon decrementing a financial account associated with thepayor. In that embodiment, the PPS server may access payor's accountinformation and determine whether the payor's account balance permitspayment request. In that embodiment, the PPS server may search withinthe user's account (e.g., through payor's linked account informationkept in the PPS databases) and decrement payor's account accordingly.

At step 203, the PPS server may generate instructions to decrement abalance value of the payor's account in accordance with the paymentrequest. Decrementing the payor's account may be accomplished using awide variety of payment methods. For example, decrementing an accountmay comprise decrementing a bank account stored in the system of recordserver of a financial institution associated with the payor. In anotherexample, the payor may create a cash account associated with the PPS(e.g., through the PPS API), which is not linked to the payor's bankaccount, and the cash account may be decremented. In yet anotherexample, decrementing payor's account may be accomplished by charging acredit card or a debit card associated with the payor. The PPS servermay also generate a payment authorization query for approval to thefinancial institute through system of record server and wait for aresponse from the system of record server to make a determination ofwhether account associated with a payor has sufficient funds. If the PPSserver determines that payor's account balance does not support thepayment request, then the PPS server may display a message indicatinginsufficient funds and/or requesting alternative payment methods.Alternatively, the PPS server may authorize the payment (e.g.,incrementing the escrow account) without first verifying whether fundsexist in the system of record server. The PPS server may also optionallyrun a predicted balance of payor's account any time a payor attempts togenerate a payment request in order to ensure that payor's accountbalance will not run below a predetermined threshold value. The PPSserver may issue a notification to the payor to confirm the transactionand/or to notify the payor of the possibility that the balance may dropbelow the predetermined threshold value. The PPS server may either denythe transaction or allow the user to proceed. Furthermore, the PPSserver may transmit a message to a third party and display options froma third party to cure the deficiency of the payment request. In oneexample, the PPS server may present an option for payment from anotheraccount. In another example, the PPS server may send an offer to open aline of credit for the payor using a third-party financial institute ora financial institute associated with the PPS. In this example, thepayor will have a line of credit, and the amount associated with thepayment request may be decremented from an account associated (e.g.,either the line of credit account or the payor's account) with the payorat a later time. For example, if a payor requests a payment of $1000,but has an account balance of less than $1000, PPS server may create aline of credit for the payor for $1000 and decrement the payor's accountat a later time by $1100 (the payment request amount and a feeassociated with creating the line of credit).

FIG. 5A-C depict a user interface displayed by payor's mobile device inorder to generate a payment request. The user interface has a firstportion 503, which is used for sending and receiving messages via theinstant messaging service application, a second portion 505, which isused for generating a message and interacting with a third partyapplication, and a third portion 506, which is used to load anapplication such as the PSS API. In this embodiment, payor 501 hasgenerated a payment request for $100. The PPS server generates a paymentauthorization query to the system of record server. The system of recordserver communicates with a financial institute associated with payor 501in order to determine whether payor 501 has sufficient funding tocomplete the payment request. In this embodiment, the PPS server doesnot receive authorization from the system of record server for a $100payment. As a result, PPS server generates instructions for payor'smobile device to display message 514 and options 512 and 516. Message514 informs payor 501 that payor 501 does not have sufficient funding tocomplete the payment request. The PPS server also generates instructionsto payor's mobile device to display two options (512 and 516) for payor501 to cure the monetary deficiency. Options 512 and 516 are generatedby the PPS server based on payor 501 account information kept in the PPSdatabase. For example payor 501 has previously registered two creditcards with the PPS. In this embodiment, the PPS server generatesinstructions to payor's mobile device to provide payor 501 with optionsto cure the funding deficiency using those credit cards. Payor 501chooses the “Amex” option (option 512). As a result, as depicted in FIG.5C, the PPS server generates instructions to charge the Amex accountassociated with payor 501 and generates instructions to payor's mobiledevice to display message 518 indicating that $100 was charged. In thisembodiment, the PPS server creates an individual escrow account forpayor 501 payment request. This escrow account is incremented by a valueof $100. In other embodiments, the amount incremented from the escrowaccount and the amount decremented from the user's account may not bethe same. An example of this may be found when there is a coupon,promotion, or other incentives. In that example, the PPS server mayincrement the escrow account by a higher or lower value than the paymentrequest indicates.

At step 204, the PPS server may generate a token string associated withthe escrow account data records. At step 205, the PPS server maygenerate a payload with a hyperlink containing the token string, textinstructions, and an image based on the payment request. In the exampleembodiment, the payload contains a hyperlink including the token string,text instructions, and an image, though the payload is not required toinclude an image or text instructions. Although an image is used in theexample embodiment, it is intended that any media element can be used,such as images (e.g., GIF, JPEG, TIFF, PNG, BMP), videos (e.g., AVI,QuickTime, Windows Media), stickers, ideograms (e.g., EMOJIs),alphanumeric characters, and links to desired websites. Although ahyperlink is used in the example embodiment, any similar functionalityto deliver a token may be used that is consistent with this disclosure.The PPS server may generate the token string comprising analphanumerical string based on a random value generator. A payload is anelectronic representation of the payment request and the escrow account,and may contain information regarding the payor, amount of the paymentrequest, and the escrow account. A token, however, may be described asan “opaque identifier” (sometimes associated with or otherwise referredto as an “opaque pointer”) of the payload that is used by the recipientto claim a payment and may not contain any information regarding theamount of the payment request. For example, the PPS server may generatea token, which only contains an alphanumerical string based on randomlygenerated values. As described below, the PPS server may use theinformation contained within the token to authenticate the activation ofthe payload. In some embodiments, neither the token, nor the payloadcontains any information regarding the amount of the payment. In suchembodiments, the payor may choose to “gift wrap” the payment and the PPSserver may not include any information regarding the payment amount inthe token or the payload, or transmit the payment amount information tothe recipient's mobile device. The recipient may receive a messagecontaining a payload with no indication of the amount of the payment.Upon successful activation of the payload, the PPS server may transmit amessage to the recipient regarding the payment amount, which, in someimplementations, may be the first moment the payment amount is revealedto the recipient. The PPS server may generate the data contained withinthe token using variety of existing methods in order to combat possiblefraud. For example, the payment token may include alphanumerical stringgenerated based on a random values. The PPS server may also create apayload comprising the token string, a graphical representation of theamount indicated by the payor to be sent, and text instructions. Thepayload may be created in a format enabled and configured to betransmitted using an instant message application. For example, thepayload may contain an image with embedded data, such as the token orother text instructions.

In another embodiment, the payor's mobile device and the PPS server maycooperate in generating the information of the payload, such that eachgenerates some or all of the information for the payload. For example,the information may be generated at the PPS server in response to arequest from the payor's mobile device to generate the payload. Forexample, the PPS server can generate a token and transmit it back to themobile device, which then selects an image and assembles a payload toinclude the token. The PPS server may generate the payload, and themobile device may add an image to the received payload; or the PPSserver may transmit payload contents, and the mobile device may assemblethe payload with an image. Alternatively, the mobile device couldgenerate the information locally via a mobile application for displaywith input from the payor. A person of ordinary skill in the art wouldunderstand that the server could generate at least part of theinformation in response to a request from the payor.

FIG. 5D depicts an embodiment of a payload generated by the PPS serverand transmitted to the payor's mobile device. In this embodiment, thePPS server generates payload 520 for payor 501 and the payment requestof $100. Payload 520 includes a graphic image representing $100 andinformation regarding payor 501. For example, payload 520 displays“Robert paid you $100” and instructions for the recipient indicatingthat the recipient may tap on the payload in order to receive thepayment. In another embodiment, payor may add comments or customize thetoken with other preferences or add special messages. In anotherembodiment, content of the token is generated such that only the PPSserver or a computer system associated with the PPS may be able toidentify the data. For example, the PPS server may store content of atoken associated with a payment request in the PPS database and, uponactivation of the token by the recipient, determine whether the contentsof the activated token and the token stored in the PPS database are thesame.

At step 206, the PPS server may transmit, or generate instructions totransmit, the payload to the payor's mobile device. The PPS server maytransmit the payload to the payor's mobile device for display in amessage field in an instant messaging service application where themobile device is configured to transmit an instant messaging containingthe token. In an embodiment, The PPS server may communicate directlywith the payor's mobile device or through the PPS API. Furthermore, inan embodiment, the PPS server may not directly send the payload to therecipient because recipient's identity is not known to the PPS server.In an embodiment, as illustrated in FIG. 5D, the PPS server may generateinstructions to the payor's mobile device to display the payload isready to be sent. For example, the PPS server, in this embodiment,generated instructions to the payor's mobile device to displayindication 519 to notifying payor 501 that the payload is ready to besent.

At step 207, the PPS server may receive instructions to increment therecipient's account. The PPS server may increment the recipient'saccount upon the recipient activating the hyperlink contained within thepayload. The PPS server may receive the instruction to increment therecipient's account from either the recipient's mobile device, thepayor's mobile device, or a third-party associated with the activationof the payload or the hyperlink contained within. For example, in anembodiment, payor's mobile device may track whether the instant messagewas transmitted and “seen” by the recipient and upon receiving theinstant message containing the payload, payor's mobile device mayinstruct the PPS server to decrement the escrow account and incrementthe recipient's account. This embodiment may be performed uponinstructions from the payor device for an automatic payment whererecipient's authorization or activation is not needed. For example, inthat embodiment, payor may choose to make the payment automatic, so thepayment will be transferred to the recipient upon the recipient openingthe instant message containing the payload. In another embodiment, theinstruction to decrement the escrow account and/or increment therecipient's account may be generated by the recipient's mobile device.In that embodiment, recipient may receive an instant message containingthe payload and upon activating the payload recipient's mobile devicemay send, using a network, the instructions to the PPS server. Anon-limiting example of activating a payload may be tapping or clickingthe payload, activating the hyperlink, or visiting a Uniform ResourceLocator (“URL”) embedded within the payload.

In an embodiment, the recipient's mobile device may activate the payloadby launching a web browser and navigating the web browser to adestination represented by the hyperlink contained within the token inorder to send an HTTP(S) request to the PPS server. The HTTP(S) requestmay be transmitted over the Internet or other communication networks,such as the mobile device communication network. In someimplementations, the PPS server may store the token content in the PPSdatabase. For example, while generating an alphanumerical string for thetoken, the PPS server may keep a record of the payload, the payor, andthe associated alphanumerical string within the token. Upon, therecipient activating the payload, the PPS server may receive the contentof the token (e.g., the alphanumerical string) and compare the activatedtoken content with the stored token content. The PPS server mayauthenticate the activation of the payload by comparing the stored tokencontent and the activated token content. Upon a positive match, the PPSserver may further generate instructions to a financial institute toincrement the recipient's account and decrement the escrow account. Insome cases, when the content of the activated token and the storedcontent of the token are not the same, then the PPS server may beconfigured to deny the payment request or generate an instruction totransmit a message to the payor mobile device indicating a failedpayment. Alternatively, the recipient's mobile device may utilize thePPS API native to an application installed and executed by therecipient's mobile device to communicate with the PPS server to activatethe hyperlink, as an alternative to navigating to a webserver URL usinga web browser. In such cases, the PPS API instructs the recipient'smobile device on communication formats and standards associated with thePPS server and local application. As such, recipient's mobile device mayuse the PPS API to activate the hyperlink and transmit the token contentdirectly to the PPS server, in a format that conforms with the PPSserver data formats, without using a web browser. This method forpayload activation may be faster because it does not require therecipient to leave the messaging application. Upon receiving the contentof the activated token, the PPS server may authenticate the contentusing the same method as described above. The PPS server may use theactivation of the token via the PPS API as the default method and usethe token activation via a web browser when the recipient's mobiledevice does not have the PPS API installed.

In another embodiment, payor may customize the payload activation byrequiring the recipient to enter a code or other authorization methods.For example, payor may require the recipient to enter a four-digit codeto activate the payload. As another example of fraud protection, theactivation process and the hyperlink creation may be done in a mannerthat clicking the URL will only result in activation of the payloadwithin the context of the received instant message environment. Forexample, if the URL is copied and pasted into a web-browser, clicking onthe link will not activate the payload.

At step 208, the PPS server may generate instructions to decrement theescrow account. In an embodiment, upon receiving instructions from therecipient's mobile device regarding the activation of the payload, thePPS server may communicate with a financial institution associated withthe recipient (either directly or through the system of record server)in order to increment recipient's account. The PPS server may alsoreceive identification information from the recipient's mobile deviceand identify the recipient using existing data stored in the PPSdatabases. If the PPS server does not have any existing stored financialinformation regarding recipient's accounts, the PPS server may generatea message to the recipient, inquiring such information. For example, thePPS server may ask the recipient to insert an account for the payment tobe transmitted to. Alternatively, the PPS server may modify paymentdates (the date that the incrementing of the recipient account occurs)based on payor's preferences, instructions, or a predicted balance. Forexample, payor may, when generating the payload, indicate that thepayment to the recipient should be delayed by a certain time or date. Asa result, the PPS server may not decrement the escrow account orincrement the recipient's account until the time condition asserted bythe payor is satisfied. In another example, if a predicted balance isbelow the predetermined amount, the PPS server may attempt to notify thepayor, or the recipient in order to avoid payor's account dropping belowa predetermined amount.

FIG. 5E-F depict a user interface for receiving a payload on therecipient's mobile device. In this embodiment, recipient 502, receivespayload 522 using an instant messaging application native to therecipient's mobile device. On the recipient's mobile device, the userinterface has a first portion 503, which is used for sending andreceiving messages via the instant messaging service application, and asecond portion 505, which is used for generating a message andinteracting with a third party application. Upon request of payor 501,payload 522 is graphically different than payload 520. Payload 522 doesnot include a graphic image that reveals the amount of the payment torecipient 502. Recipient 502, activates payload 522 by tapping on theimage. Upon this activation, the PPS server is notified and receives aninstruction to increment an account associated with recipient 502. ThePPS server searches within the PPS database and does not find anyinformation associated with recipient 502. As a result, server 104displays message 524 indicating that recipient 502 must update financialinformation of the PPS API (e.g., Cash App or an account associated withthe recipient). Upon recipient 502 updating the requested information,the PPS server in the depicted embodiment, increments an accountassociated with recipient 502 and decrements the escrow accountassociated with the payment request. The PPS server may also send aconfirmation to payor's mobile.

Referring now to FIG. 3 a flowchart depicting operational steps of amethod for generating and transmitting a payload is illustrated inaccordance with an embodiment. Steps of method 300 may be implementedusing one or more modules of a computing system such the mobile deviceserver. The mobile device server may generate instructions to payor'smobile device or the recipient's mobile device, or communicate with thePPS server as depicted in FIG. 1 . FIG. 3 does not imply any limitationswith regard to the environments or embodiments that may be implemented.Modifications to the depicted environment or embodiment shown in FIG. 3may be made.

At step 301, the mobile device server may generate instructions to thepayor's mobile device to display a first screen portion configured todisplay received and sent instant messages and receive commands totransmit an instant message to a message service server. The mobiledevice server may use an instant messaging application/platform nativeto a particular operating system for payor's mobile device.Alternatively, the mobile device may use another third-party instantmessaging or other communication application that is not native to theoperating system of the mobile device. FIG. 5A is an example of a userinterface displayed on payor's mobile device based on instructions fromthe mobile device server. In this embodiment, payor's mobile device isinstructed, by the mobile device server, to generate a screen portionsuch as FIG. 5A, which indicates that payor 501 may communicate withrecipient 502 via an instant messaging application.

At step 302, the mobile device server, may generate instructions for thepayor's mobile device to display a second screen portion configured toaccess a third-party application and configured to populate a newmessage with a payload and at step 303, the mobile device server mayreceive an inputted amount in the second screen portion. Payor's mobiledevice may indicate to the payor mobile device is capable ofcommunication with a third party application (such as PPS API) in orderto generate messages with a payload by displaying a graphic icon orsending a notification to the payor. Mobile payor's mobile device mayalso receive an inputted amount from the payor s indicating an amountfor a payload.

FIG. 5A depicts an embodiment for a user interface, displayed on payor'smobile device, in order to generate a payment request. In thisembodiment, payor 501 is using a mobile device that is configured tosend and receive instant messages and enabled to communicate with thePPS server or other third party applications. In the depictedembodiment, the instant messaging application is linked with anapplication that could directly communicate with the PPS server. Payor'smobile device indicates to payor 501 that the instant messagingapplication is enabled to communicate with the PPS server or anapplication directly linked to the PPS (e.g., the PPS API) in order tocreate and transmit a payload by displaying graphic 504. In the depictedembodiment, payor 501 indicates an inclination to initiate a paymentrequest by tapping/clicking on graphic 504. Upon receiving thisindication, the PPS server, generates instructions to payor's mobiledevice to display boxes 508, and 510. Box 508 indicates the amount ofthe payment request and is configured to receive input from payor 501for modification of the amount. Box 510 inquires confirmation that apayment for the amount disclosed in box 508 may be sent to the PPSserver. In the embodiment depicted in FIG. 5A, payor 501 chooses $100 tosend to recipient 502 and clicks on box 510 in order to confirm thepayment request. In an embodiment, third portion 506 displays to thepayor 501 an option to be transferred to or open a user interface of themobile application directly in communication with the PPS server (e.g.,PPS API) in order to modify several options such as payment method,account information, or other user preferences. In an embodiment, payor501 may activate the third portion 506 by clicking or tapping on thegraphic icon presented in the third portion 506. Upon payor 501activating the third portion 506, the PPS API may be loaded. At step304, the mobile device server may transmit, to the PPS, a requestcontaining the inputted amount and an identification of the payor. Asdescribed in FIG. 2 (step 201), payor's mobile device may, receiveinstructions from the mobile device server, to use the PPS network orany other communication methods to communicate with the PPS server. Inanother embodiment, payor's mobile device may use the PPS API tocommunicate with the PPS server. The PPS server may receive a paymentrequest from payor's mobile device. The payment request may compriseinformation regarding payment (e.g., methods of payment, and amount ofpayment) and user identification (e.g., name and other informationassociated with the payor for the PPS server to identify an accountassociated with the payor). In the embodiment depicted in FIG. 5A-E,payor's mobile device sends a payment request for $100 to the PPS serverand includes information associated with payor 501. In an embodiment,payor's mobile device may not send any information regarding therecipient to the PPS server. For example in the depicted embodiment,payor's mobile device does not send any information regarding recipient502 to the PPS server.

Furthermore, the mobile device server may also transmit other userpreferences with the payment request. In an embodiment, a payor maychoose from a pre-generated list of payload images or choose to create anew payload image. In another embodiment, a payor may choose to not haveany image or text associated with the payload. The information (e.g., animage or text) may be collected by the mobile device and added to thepayload after receiving the token from the PPS server. For example, apayor may (manually or automatically) choose an image depicting a $100bill for a payment request of $100 or customize an image based on theamount of the payment request, such as the image represented in payload520. The mobile device generates a payload using a token from the PPSserver, text instructions, and the selected image. In other embodiments,a payor may upload an image locally using the payor's mobile device orfrom a network (e.g., mobile device server). In one configuration, themobile device server may receive the image from the mobile device andtransmit the image to the PPS server, and receive a payload containingthat image. In another configuration, the mobile device may select animage, transmit the image to the PPS server, and the PPS server maygenerate the payload and transmit it to the mobile device. Additionally,a payor may change the image after receiving the payload containing theimage. In that example, a payor may change the payload image, or thetext instructions, before sending the payload using the instantmessaging application. In another embodiment, the payor may choose toadd other media elements to the payload.

At step 305, the mobile device server may receive a payload containing ahyperlink with a token string, an image based on the inputted amount ofa payment request, and instructions for payment. As explained in FIG. 2(steps 204-5), the PPS server may generate a payload containing a tokenstring and other payment information and transmit the payload to thepayor's mobile device using a variety of communication methods namelythe PPS network.

At step 306, mobile device server may generate instructions to payor'smobile device to populate a message to the recipient in the first screenportion containing the payload without an identifier of the recipient.Payor's mobile device may, upon receiving payload 520, generate a screenportion such as the screen portion depicted in FIG. 5D, which includesinformation regarding the recipient 502, payload 520, and an indicationsuch as indication 519 that conveys to payor 501 that payload 520, inform of a text message, is ready to be sent. In the depicted embodiment,payor's mobile device populates this message within the context of thesame instant messaging application as depicted in FIG. 5A. In otherembodiment, the message contains the payload and may be populated withina different instant messaging application native to payor's mobiledevice. This may be due to differences within user preferences (payor orrecipient) or due to difference between operating devices associatedwith mobile devices of the payor and the recipient. For example, if thepayor has a mobile device with an iOS operating system and the recipienthas a mobile device with an Android operating system. Payor's mobiledevice may generate a message to the payor indicating that the payloadmay not be sent or, because iOS and Android use different instantmessaging applications, populate the message containing the payloadwithin a third party instant messaging application native to both mobiledevices.

At step 307, mobile device server may transmit the instant messagecontaining the payload to the recipient's mobile device. The payor'smobile device may use variety of communication methods to communicatewith recipient's mobile device in order to transmit the message,containing the payload, to recipient's mobile device. In the depictedenvironment, payor's mobile device and recipient's mobile device bothutilize the iOS operating system. As mentioned previously, payor'smobile device often cannot or will not send the payload directly to therecipient's mobile device via the PPS network; rather, the payor'smobile device indirectly communicates the payload to the recipient'smobile device via the mobile device network. As a result, the PPS maynot receive any information regarding the recipient until the payload isactivated and accessed by the recipient mobile device. In someimplementations, the payor's mobile device may transmit a recipientidentifier to the PPS server. The recipient identifier may containinformation regarding the recipient's mobile device, the payor's mobiledevice, recipient's account, and/or other information regarding thepayment request. The recipient identifier maybe unique or may helpidentify each device. Non-limiting examples of such identifiers mayinclude unique device identifier (UDID), media access control (MAC)address or identifier, phone number, user ID, and manufacturing serialnumber, among others. For example, a recipient identifier may includethe phone number of the payor and the amount of the payment request. ThePPS server may, upon a successful and authenticated activation of apayload, add relevant information regarding the recipient to therecipient identifier. In other words, information associated with therecipient may be transmitted to the PPS server and the recipient is nolonger “unknown” to the PPS server after receiving the first paymentbecause the PPS server may store the identifying information for therecipient mobile device. In some implementations, the PPS server mayutilize the recipient identifier in a fraud prevention system. Forexample, the PPS server may track recipient identifiers for a particularpayor over time and develop a pattern for the payor's payments (e.g., apayor pays $100 on the same day of the month to someone having the samerecipient identifier). In that example, the PPS server may deny asimilar transaction to a person having a different recipient identifier.

Referring now to FIG. 4 , a flowchart depicting operational steps of amethod for transmitting a message containing a payload is illustrated inaccordance with an embodiment. Steps of method 400 may be implementedusing one or more modules of a mobile device server or a network such asthe mobile device network. FIG. 4 does not imply any limitations withregard to the environments or embodiments that may be implemented.Modifications to the depicted environment or embodiment shown in FIG. 4may be made.

At step 401 the mobile device network may receive a request to transmita message generated on a payor's mobile device comprising a payload witha hyperlink containing a token string, image based on a payment requestamount, and text instructions for receiving a payment to a recipientwhere the payload does not include the recipient's identification.Generation and customization of payloads and tokens are described inFIG. 2 and FIG. 3 . The mobile device server may host an instantmessaging platform that is used by both the payor's mobile device andthe recipient's mobile device. The mobile device network may receive aninstruction from a mobile device such as the payor's mobile device totransmit a message that contains a payload on said instant messagingplatform. In an embodiment, the mobile device network may only receivean identifier for the recipient such as a phone number and not any otherinformation regarding the payload. For example, the mobile devicenetwork will receive identification (e.g., phone number) of therecipient as a part of the instructions to deliver the text message;however, the mobile device network will not receive informationregarding the content of instant message. In an embodiment, the mobiledevice network may treat the payload as a black box being deliveredwithout knowing the content of the black box. At step 402, the mobiledevice network may transmit, the message using an instant messagingapplication on payor's mobile device to the recipient's mobile device.The mobile device network may use an instant messaging applicationplatform native to both payor and recipient's mobile devices. In anembodiment, while the content of the token may not be encrypted, themessage may contain sensitive information regarding the payor and therecipient. In that embodiment, rather than encrypt portions or all ofthe payload content, the PPS server may rely on security procedures andprotocols native to the mobile device network; for instance, the mobiledevice network may encrypt some or all of the message portions (e.g.,payload) when the message is generated and transmitted to the recipientmobile device. Therefore, the mobile device network may encrypt themessage to ensure proper and safe transmission. The PPS server may thenrely on that fraud protection method and increment an account associatedwith a device that has activated the payload.

Although certain illustrative, non-limiting exemplary embodiments havebeen presented, various changes, substitutions, permutations, andalterations may be made without departing from the scope of the appendedclaims. Further, the steps of the methods described herein may becarried out in any suitable order, or simultaneously where appropriate.Thus, the scope of the disclosure should not necessarily be limited bythis description.

Unless specifically stated otherwise as apparent from the followingdiscussion, it is appreciated that throughout the description,discussions utilizing terms such as “processing,” “computing,”“transmitting,” “receiving,” “determining,” “displaying,” “identifying,”“presenting,” “establishing,” or the like, may refer to the action andprocesses of a data processing system, or similar electronic device thatmanipulates and transforms data represented as physical (electronic)quantities within the system's registers and memories into other datasimilarly represented as physical quantities within the system'smemories or registers or other such information storage, transmission ordisplay devices. The system or portions thereof may be installed on anelectronic device.

The exemplary embodiments may relate to an apparatus for performing oneor more of the functions described herein. This apparatus may bespecially constructed for the required purposes, or it may comprise aspecial purpose computer selectively activated or reconfigured by acomputer program stored in the computer. Such a computer program may bestored in a machine (e.g., computer) readable storage medium, such as,but is not limited to, any type of disk including floppy disks, opticaldisks, CD-ROMs and magnetic-optical disks, read only memories (ROMs),random access memories (RAMs) erasable programmable ROMs (EPROMs),electrically erasable programmable ROMs (EEPROMs), magnetic or opticalcards, or any type of media suitable for storing electronic instructionsfor operations on a processor, and each coupled to a bus.

The exemplary embodiments described herein are described as softwareexecuted on at least one server, though it is understood thatembodiments may be configured in other ways and retain functionality.The embodiments may be implemented on known devices such as a personalcomputer, a special purpose computer, cellular telephone, personaldigital assistant (“PDA”), a digital camera, a digital tablet, anelectronic gaming system, a programmed microprocessor or microcontrollerand peripheral integrated circuit element(s), and ASIC or otherintegrated circuit, a digital signal processor, a hard-wired electronicor logic circuit such as a discrete element circuit, a programmablelogic device such as a PLD, PLA, FPGA, PAL, or the like. In general, anydevice capable of implementing the processes described herein may beused to implement the systems and techniques according to thisdisclosure.

The exemplary embodiments may relate to an apparatus for performing oneor more of the functions described herein. This apparatus may bespecially constructed for the required purposes or be selectivelyactivated or reconfigured by computer executable instructions stored innon-transitory computer memory medium or non-transitorycomputer-readable storage medium.

It is to be appreciated that the various components of the technologymay be located at distant portions of a distributed network or theInternet, or within a dedicated secured, unsecured, addressed/encoded orencrypted system. Thus, it should be appreciated that the components ofthe system may be combined into one or more devices or co-located on aparticular node of a distributed network, such as a telecommunicationsnetwork. As will be appreciated from the description, and for reasons ofcomputational efficiency, the components of the system may be arrangedat any location within a distributed network without affecting theoperation of the system. Moreover, the components could be embedded in adedicated machine.

Furthermore, it should be appreciated that the various links connectingthe elements may be wired or wireless links, or any combination thereof,or any other known or later developed element(s) that is capable ofsupplying or communicating data to and from the connected elements. Theterm “module” as used herein may refer to any known or later developedhardware, software, firmware, or combination thereof that is capable ofperforming the functionality associated with that element.

All references, including publications, patent applications, andpatents, cited herein are hereby incorporated by reference to the sameextent as if each reference were individually and specifically indicatedto be incorporated by reference and were set forth in its entiretyherein.

The use of the terms “a” and “an” and “the” and similar referents in thecontext of describing the invention (especially in the context of thefollowing claims) are to be construed to cover both the singular and theplural, unless otherwise indicated herein or clearly contradicted bycontext. The terms “comprising,” “having,” “including,” and “containing”are to be construed as open-ended terms (i.e., meaning “including, butnot limited to,”) unless otherwise noted. Recitation of ranges of valuesherein are merely intended to serve as a shorthand method of referringindividually to each separate value falling within the range, unlessotherwise indicated herein, and each separate value is incorporated intothe specification as if it were individually recited herein. All methodsdescribed herein may be performed in any suitable order unless otherwiseindicated herein or otherwise clearly contradicted by context. The useof all examples, or exemplary language (e.g., “such as”) providedherein, is intended merely to better illuminate the disclosure and doesnot pose a limitation on the scope of the disclosure unless otherwiseclaimed. No language in the specification should be construed asindicating any non-claimed element as essential to the practice of thedisclosure.

Presently preferred embodiments of this disclosure are described herein,including the best mode known to the inventors for carrying out thedisclosure. Variations of those preferred embodiments may becomeapparent to those of ordinary skill in the art upon reading theforegoing description. The inventors expect skilled artisans to employsuch variations as appropriate, and the inventors intend for thedisclosure to be practiced otherwise than as specifically describedherein. Accordingly, this disclosure includes all modifications andequivalents of the subject matter recited in the claims appended heretoas permitted by applicable law. Moreover, any combination of theabove-described elements in all possible variations thereof isencompassed by the disclosure unless otherwise indicated herein orotherwise clearly contradicted by context.

Although the present technology has been described in detail for thepurpose of illustration based on what is currently considered to be themost practical and preferred implementations, it is to be understoodthat such detail is solely for that purpose and that the technology isnot limited to the disclosed implementations, but, on the contrary, isintended to cover modifications and equivalent arrangements that arewithin the spirit and scope of the appended claims. For example, it isto be understood that the present technology contemplates that, to theextent possible, one or more features of any implementation may becombined with one or more features of any other implementation.

What is claimed is:
 1. A method, implemented at least in part by one ormore computing devices of a payment processing service, comprising:receiving, from a sender device of a sender, a request to initiate atransfer of an asset to a recipient; causing a user interface to bepresented via a display of the sender device, the user interfaceconfigured to receive an input of an amount of the asset to betransferred; causing an indication of the transfer of the asset to bepresented via the user interface, the indication of the transfer of theasset presented in association with a graphical icon representing a giftwrapping that conceals at least some information regarding a payloadassociated with the transfer; associating the graphical icon with thepayload associated with the transfer to generate a gift-wrapped elementthat includes (i) the amount and (ii) the at least some informationregarding the payload; causing a notification to be sent, via anapplication on the sender device, to a recipient device of therecipient, wherein the notification includes the gift wrapped element;and causing assets in the amount to be withdrawn from an account of thesender and transferred to an account of the recipient.
 2. The method ofclaim 1, wherein the application is a native messaging application onthe sender device and the recipient receives the notification via acorresponding native messaging application on the recipient device. 3.The method of claim 1, wherein the application is a non-native messagingapplication on the sender device and the recipient receives thenotification via a corresponding native messaging application on therecipient device.
 4. The method of claim 1, wherein the assets in theamount are withdrawn upon receiving an indication of acceptance of thegift-wrapped element from the recipient device.
 5. The method of claim1, wherein the notification is sent upon receiving a request to transmitthe gift-wrapped element to the recipient device.
 6. The method of claim1, further comprising: generating instructions causing the sender deviceto display a virtual option for the sender to pay for the amount.
 7. Themethod of claim 1, wherein the payload includes a hyperlink associatedwith the asset.
 8. A payment service system, comprising: one or morememories having computer-readable instructions stored therein; and oneor more processors configured to execute the computer-readableinstructions to: generate a user interface to be presented on a displayof a sender device of a sender, the user interface configured to receivean input of an amount of an asset to be transferred to an account of arecipient; present, on the user interface, a graphical icon representinga gift wrapping that conceals at least some information regarding apayload associated with the transfer; generate a gift-wrapped elementusing the graphical icon that includes (i) the amount and (ii) the atleast some information regarding the payload; cause a notification to besent, via an application on the sender device, to a recipient device ofthe recipient, wherein the notification includes the gift-wrappedelement; and cause assets in the amount to be withdrawn from an accountof the sender and transferred to an account of the recipient.
 9. Thepayment service system of claim 8, wherein the application is a nativemessaging application on the sender device and the recipient receivesthe notification via a corresponding native messaging application on therecipient device.
 10. The payment service system of claim 8, wherein theapplication is a non-native messaging application on the sender deviceand the recipient receives the notification via a corresponding nativemessaging application on the recipient device.
 11. The payment servicesystem of claim 8, wherein the assets in the amount are withdrawn uponreceiving an indication of acceptance of the gift-wrapped element fromthe recipient device.
 12. The payment service system of claim 8, whereinthe notification is sent upon receiving a request to transmit thegift-wrapped element to the recipient device.
 13. The payment servicesystem of claim 8, wherein the one or more processors are configured toexecute the computer-readable instructions to cause the sender device todisplay a virtual option for the sender to pay for the amount.
 14. Thepayment service system of claim 8, wherein the payload includes ahyperlink associated with the asset.
 15. One or more non-transitorycomputer-readable media comprising computer-readable instructions, whichwhen executed by one or more processors of a payment service system,cause the payment service system to: receive, from a sender device of asender, a request to initiate a transfer of an asset to a recipient;cause a user interface to be presented via a display of the senderdevice, the user interface configured to receive an input of an amountof the asset to be transferred; cause an indication of the transfer ofthe asset to be presented via the user interface, the indication of thetransfer of the asset presented in association with a graphical iconrepresenting a gift wrapping that conceals at least some informationregarding a payload associated with the transfer; associate thegraphical icon with the payload associated with the transfer to generatea gift-wrapped element that includes (i) the amount and (ii) the atleast some information regarding the payload; cause a notification to besent, via an application on the sender device, to a recipient device ofthe recipient, wherein the notification includes the gift-wrappedelement; and cause assets in the amount to be withdrawn from an accountof the sender and transferred to an account of the recipient.
 16. Theone or more non-transitory computer-readable media of claim 15, whereinthe application is a native messaging application on the sender deviceand the recipient receives the notification via a corresponding nativemessaging application on the recipient device.
 17. The one or morenon-transitory computer-readable media of claim 15, wherein theapplication is a non-native messaging application on the sender deviceand the recipient receives the notification via a corresponding nativemessaging application on the recipient device.
 18. The one or morenon-transitory computer-readable media of claim 15, wherein the assetsin the amount are withdrawn upon receiving an indication of acceptanceof the gift-wrapped element from the recipient device.
 19. The one ormore non-transitory computer-readable media of claim 15, wherein thenotification is sent upon receiving a request to transmit thegift-wrapped element to the recipient device.
 20. The one or morenon-transitory computer-readable media of claim 15, wherein theexecution of the computer-readable instruction by one or more processorsfurther causes the payment service to cause the sender device to displaya virtual option for the sender to pay for the amount.